Incidents created by Jira Cloud integration are not re-triggered after changing status

#1

Incidents created by Jira Cloud integration are not re-triggered after changing status to Blocker one more time

I found some problem with Jira Cloud - PagerDuty integration:

  1. I created a blocker in Jira -> An Incident was created automatically at PD
  2. I resolved this incident
  3. I updated Jira status to Normal
  4. After some time I changed status of Jira to Blocker again.
  5. An Incident was not populated at PD

I expect that on 5th step I will see an active incident again but I don’t.

Is it possible to do it?

Thanks, Andrey Topchiy

#2

HI Andrey,

This is not yet possible I am afraid but I will pass along the information to our product team who works with this integration and let them know what you are looking for.

Sorry we cannot help you out with this right now, but do let me know if you have any more questions.

John

#3

Hi John! Thank you for reply.

Such functionality will be very popular because it is not rare situation when status of jira issue can be changed several times (e.g. if issue moved to other func team)

Thanks, Andrey Topchiy

#4

Thanks Andrey!

Understood - I will most definitely pass this along.

John

#5

Hi PagerDuty Support Team,

Has this feature been implemented yet? Is there any way to re-trigger an alert if the ticket in Jira is escalated?

#6

Hello Matt,

Sorry to say this has not been implemented but I have added your +1 to the feature request.

John

1 Like